Remove ROS1 driver status publisher #66
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dge/carma_carla_driver_status
9 tasks
|
Closing the PR since the root cause is identified to lie somewhere else |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Description
Supports this PR:
usdot-fhwa-stol/carma-platform#2247
Related GitHub Issue
usdot-fhwa-stol/carma-platform#2186
Related Jira Key
TODO
Motivation and Context
Integration testing VRU use case - platform is timing out due toe driver status messages being dropped over the ros1_bridge depending on the PCs
How Has This Been Tested?
Simulation PC 1
Types of changes
Checklist: